Products
In-IDE
IDE extension that lets you fix coding issues before they exist!
Discover SonarQube for IDE
SaaS
Setup is effortless and analysis is automatic for most languages
Discover SonarQube Cloud
Self-Hosted
Fast, accurate analysis; enterprise scalability
Discover SonarQube Server

Secrets
ABAP
Ansible
Apex
AzureResourceManager
C
C#
C++
CloudFormation
COBOL
CSS
Dart
Docker
Flex
GitHub Actions
Go
HTML
Java
JavaScript
JSON
JCL
Kotlin
Kubernetes
Objective C
PHP
PL/I
PL/SQL
Python
RPG
Ruby
Rust
Scala
Shell
Swift
Terraform
Text
TypeScript
T-SQL
VB.NET
VB6
XML
YAML

ABAP static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your ABAP code

Tags

Impact

Clean code attribute

Standard tables should be searched using "BINARY SEARCH"
Code Smell
"WHEN OTHERS" clauses should be last
Code Smell
Cognitive Complexity of functions should not be too high
Code Smell
"LIKE" clauses should not be used without wildcards
Code Smell
Jump statements should not be redundant
Code Smell
"JOIN" should be used instead of nested "SELECT" statements
Code Smell
"SELECT INTO TABLE" should be used
Code Smell
"EXIT" and "CHECK" statements should not be used in "SELECT" loops
Code Smell
Duplications in driver tables should deleted before the tables are used
Code Smell
Two branches in a conditional structure should not have exactly the same implementation
Code Smell
SQL "LIKE" clauses should not start with wildcard characters
Code Smell
Unnecessary chain syntax should not be used
Code Smell
Asterisks should be used for headers and to comment out code
Code Smell
"CX_ROOT" should not be caught
Code Smell
Mass operations should be used with internal tables instead of loops
Code Smell
"SORTED" or "HASHED" internal tables should be accessed with a key
Code Smell
Keywords should not be used as variable names
Code Smell
"FORM... ENDFORM" and "PERFORM" should not be used
Code Smell
"NOT IN" should not be used
Code Smell
A SQL "SELECT" statement should not involve too many tables
Code Smell
Macros should be documented
Code Smell
Functions should be documented
Code Smell
Forms should be documented
Code Smell
Classes should be documented
Code Smell
"DATA" variable names should comply with a naming convention
Code Smell
Report names should comply with a naming convention
Code Smell
Macro names should comply with a naming convention
Code Smell
Function names should comply with a naming convention
Code Smell
Cyclomatic Complexity of functions should not be too high
Code Smell
"REFRESH itab FROM TABLE" should not be used
Code Smell
"%_HINTS" should not be used
Code Smell
"SY-SUBRC" should be tested after each statement setting it.
Code Smell
Form names should comply with a naming convention
Code Smell
Internal source code processing statements should not be used
Code Smell
System C functions should not be used
Code Smell
Native SQL should not be statically embedded
Code Smell
SQL aggregate functions should not be used to prevent bypassing the SAP buffer
Code Smell
To "SELECT", "INSERT" or "DELETE" several lines in databases, internal tables should be used in place of loop control structure
Code Smell
SQL "DISTINCT" operator should not be used to prevent bypassing the SAP buffering
Code Smell
Columns to be read with a "SELECT" statement should be clearly defined
Code Smell
The "LIKE" operator should be used very carefully in SQL "WHERE" condition
Code Smell
Subqueries and "JOIN" clauses should not be used
Code Smell
"REFRESH itab" should not be used
Code Smell
"SYSTEM-CALL" statement should not be used
Code Smell
"DATA BEGIN OF OCCURS" should not be used
Code Smell
Unused local variables should be removed
Code Smell
Loops should not contain more than a single "CONTINUE", "EXIT", "CHECK" statement
Code Smell
Control flow statements "IF", "CASE", "DO", "LOOP", "SELECT", "WHILE" and "PROVIDE" should not be nested too deeply
Code Smell
Cyclomatic Complexity of methods should not be too high
Code Smell
Cyclomatic Complexity of classes should not be too high
Code Smell
"CASE" statements should have "WHEN OTHERS" clauses
Code Smell
"CASE statements should have at least 3 "WHEN" clauses
Code Smell
"IF ... ELSEIF" constructs should end with "ELSE" clauses
Code Smell
Sections of code should not be commented out
Code Smell
Subroutine parameters should be passed by reference rather than by value
Code Smell
Statements should be on separate lines
Code Smell
String literals should not be duplicated
Code Smell
Interface names should comply with a naming convention
Code Smell
SQL EXISTS subqueries should not be used
Code Smell
Redundant pairs of parentheses should be removed
Code Smell
Magic numbers should not be used
Code Smell
Nested blocks of code should not be left empty
Code Smell
Expressions should not be too complex
Code Smell
Mergeable "if" statements should be combined
Code Smell
Tabulation characters should not be used
Code Smell
Files should not have too many lines of code
Code Smell
Lines should not be too long
Code Smell
Class names should comply with a naming convention
Code Smell
Method names should comply with a naming convention
Code Smell

System C functions should not be used

consistency - conventional

maintainability

Code Smell

lock-in

Why is this an issue?

According to the SAP documentation:

System functions are only intended for internal usage. Incompatible changes and further development is possible at any time and without warning or notice.

So calling system C functions using a CALL statement should be avoided.

Noncompliant code example

CALL 'MULTIPLY' ID 'P1'  FIELD '9999'
                ID 'P2'  FIELD '9999'
                ID 'RES' FIELD RESULT.

Available In:

Catch issues on the fly,
in your IDE

Detect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

Analyze code in your
on-premise CI

Developer Edition
Available Since
9.1

In-IDE

SaaS

Self-Hosted